Subject: Minutes from the APPN MIB BOF and HPR MIB BOF

From: "Richard L. Daugherty ((919) 254-6838)" <[email-masked]>
Date: Wed, 17 May 95 10:36:07 EDT

This report covers both the APPN MIB BOF (Tuesday night) and the
HPR MIB BOF (Wednesday night).  It presents the results as if
only one meeting occurred.

Both BOFs quickly determined that interest in the creation of
MIBs for APPN and HPR existed.

IBM's submissions were reviewed and then accepted as the starting
documents for the AIW's work.  (See below for technical comments
related to the MIBs.)

A SIG charter and schedule were created for presentation to the
AIW.  These were approved by the AIW on Thursday, creating the
APPN/HPR MIB SIG.

Charter:  Produce AIW approved MIBs for APPN and HPR.  The MIBs
should allow for monitoring and control of APPN and HPR using
SNMP.  The two produced MIBs should be separate documents.  They
should reference the appropriate related MIBs.  The AIW-produced
MIBs will be submitted to the IETF for standardization.

Schedule:
Date          APPN MIB    HPR MIB
June '95      AD
Aug AIW                   AD
Nov AIW       AP
Spring '96    CP          AP
AIW
Summer '96                CP
AIW
MIBs will be submitted to IETF
after AIW AP approval.

Additional dates:
Item                            Date
.0 draft - APPN MIB             done (ibm removed from
                                prefix of variable names)
.1 draft - APPN MIB             5/30/95
Request AD on .1 draft          6/95
Review .2 APPN MIB draft        8/95 @ AIW
Initial submission of APPN MIB  12/95
to IETF
Initial submission of HPR MIB   4/96
to IETF

E-Mail and FTP:
Mailing list name --  aiw-appn-mibs
     Everyone who signed the "attendance sheets" at the two BOFs
     have been subscribed to the new mailing list.
FTP Directory -- aiw/appn/mibs
     APPN MIB draft .0   - aiw/appn/mibs/appn.mib.0
     HPR MIB draft .0    - aiw/appn/mibs/hpr.mib.0

Technical comments on the MIBs:
Unless otherwise stated, all comments are assumed to apply to
both MIBs.

The MIB needs to be updated to use SNMP V2 objects.  (e.g.,
gauge32)

The MIB anchor point will need to eventually be moved out of the
enterprise space.

The MIB variables should not start with "ibm".

Discussion on the relationship to the IF interface table.  (I
personally did not follow all of this discussion point.
Subsequent discussion between the main parties resolved the
concerns.  No change to the MIBs is proposed/required by the
resolution.)

APPN MIB - link station (p6) - the link station information needs
to be coordinated with the IETF DLC MIBs.

APPN MIB - APPN SNMP Performance (p7) these objects can be
dropped.

APPN MIB - FRSN and Name TG tables (p10) the duplicate
information should be folded into one table, with the other table
providing a "pointer".

HPR MIB - a trap should be added for path switch.

HPR MIB - additional information/guidance needs to be added on
when an entry is placed in the RTP status table.

HPR MIB - OID in NCL table.

HPR MIB - traps corresponding to the HPR alerts should be added.

Work assignments:
Solicit vendor enhancements to base MIBs: - Rich Daugherty

Identify overlay and proposed relationship to other MIBs:
     DLC MIB - Wayne Clark
     SNA NAU and APPC MIBs - Zbigniew Kielczewski

Check recent APPN architecture activity for any additional MIB
hits:
     IBM
     DCL

Rich Daugherty